View EPC2TI32_6302698.PDF datasheet online --- IC-ON-LINE

Datasheet File OCR Text:

january 2012 altera corporation cf52005-3.0 datasheet ? 2012 altera corporation. all rights reserved. altera, arria, cyclone, hardcopy, max, megacore, nios, quartus and stratix words and logos are trademarks of altera corporation and registered in the u.s. patent and trademark office and in other countries. all other words and logos identified as trademarks or service marks are the property of their respective holders as described at www.altera.com/common/legal.html . altera warrants performance of its semiconductor products to current specifications in accordance with altera's standard warranty, but reserves the right to make changes to any products and services at any time without notice. altera assumes no responsibility or liability arising out of the application or use of any information, product, or service described herein except as expressly agreed to in writing by altera. altera customers a re advised to obtain the latest version of device specifications before relying on any published information and before placing or ders for products or services. 101 innovation drive san jose, ca 95134 www.altera.com subscribe iso 9001:2008 registered configuration devices for sram-based lut devices this datasheet describes configuration devices for sram-based look-up table (lut) devices. supported devices ta b l e 1 lists the supported altera ? configuration devices. features configuration devices for sram-based lut devices offer the following features: configures altera acex ? 1k, apex ? 20k (including apex 20k, apex 20kc, and apex 20ke), apex ii, arria ? gx, cyclone ? , cyclone ii, flex ? 10k (including flex 10ke and flex 10ka) mercury ? , stratix ? , stratix gx, stratix ii, and stratix ii gx devices easy-to-use four-pin interface low current during configuration and near-zero standby mode current programming support with the altera programming unit (apu) and programming hardware from data i/o, bp microsystems, and other third-party programmers available in compact plastic packages 8-pin plastic dual in-line (pdip) package 20-pin plastic j-lead chip carrier (plcc) package 32-pin plastic thin quad flat pack (tqfp) package epc2 device has reprogrammable flash configuration memory table 1. altera configuration devices device memory size (bits) isp support cascaded support reprogrammable recommended operating voltage (v) epc1 1,046,496 no yes no 5.0 or 3.3 epc2 1,695,680 yes yes yes 5.0 or 3.3 epc1064 65,536 no no no 5.0 epc1064v 65,536 no no no 3.3 epc1213 212,942 no yes no 5.0 epc1441 440,800 no no no 5.0 or 3.3
page 2 functional description configuration devices for sram-based lut devices january 2012 altera corporation 5.0-v and 3.3-v in-system pr ogrammability (isp) through the built-in ieee std. 1149.1 jtag interface built-in jtag boundary-scan test (bst) circuitry compliant with ieee std. 1149.1 supports programming through serial vector format file ( .svf ), jam ? standard test and programming language (stapl) format file ( .jam ), jam byte code file ( .jbc ), and the quartus ? ii and max+plus ? ii softwares using the usb-blaster ? , masterblaster ? , byteblaster ? ii, ethernetblaster, or byteblastermv ? download cable supports programming through programmer object file ( .pof ) for epc1 and epc1441 devices n init _ conf pin allows init _ conf jtag instruction to begin fpga configuration f for more information about enhanced configuration (epc) devices, refer to the enhanced configuration (epc) devices datasheet . f for more information about serial configuration (epcs) devices, refer to the serial configuration (epcs) devices datasheet . functional description with sram-based devices, configuration data must be reloaded each time the device powers up, the system initializes, or when new configuration data is needed. altera configuration devices store configuration data for sram-based acex 1k, apex 20k, apex ii, arria gx, cyclone, cyclone ii, flex 10k, flex 6000, mercury, stratix, stratix gx, stratix ii, and stratix ii gx devices. ta b l e 2 lists the supported configuration devices required to configure the acex 1k, apex 20k, apex 20kc, apex 20ke, apex ii, cyclone, cyclone ii , flex 10k, flex 10ka, flex 10ke, flex 6000/a, flex 8000a, mercury, stratix, stratix gx, or stratix ii device. table 2. supported configuration devices (part 1 of 4) device family device data size (bits) (1) epc1064 or epc1064v epc1213 epc1441 epc1 epc2 acex 1k ep1k10 159,160 ? ? 1 1 1 ep1k30 473,720 ? ? ? 1 1 ep1k50 784,184 ? ? ? 1 1 ep1k100 1,335,720 ? ? ? ? 1 apex 20k ep20k100 993,360 ? ? ? 1 1 ep20k200 1,950,800 ? ? ? ? 2 ep20k400 3,880,720 ? ? ? ? 3 apex 20kc ep20k200c 1,968,016 ? ? ? ? 2 ep20k400c 3,909,776 ? ? ? ? 3 ep20k600c 5,673,936 ? ? ? ? 4 ep20k1000c 8,960,016 ? ? ? ? 6
functional description page 3 configuration devices for sram-based lut devices january 2012 altera corporation apex 20ke ep20k30e 354,832 ? ? 1 1 1 ep20k60e 648,016 ? ? ? 1 1 ep20k100e 1,008,016 ? ? ? 1 1 ep20k160e 1,524,016 ? ? ? ? 1 ep20k200e 1,968,016 ? ? ? ? 2 ep20k300e 2,741,616 ? ? ? ? 2 ep20k400e 3,909,776 ? ? ? ? 3 ep20k600e 5,673,936 ? ? ? ? 4 ep20k1000e 8,960,016 ? ? ? ? 6 ep20k1500e 12,042,256 ? ? ? ? 8 apex ii ep2a15 1,168,688 ? ? ? ? 3 ep2a25 1,646,544 ? ? ? ? 4 ep2a40 2,543,016 ? ? ? ? 6 ep2a70 4,483,064 ? ???11 cyclone ep1c3 627,376 ? ? ? 1 1 ep1c4 925,000 ? ? ? 1 1 ep1c6 1,167,216 ? ? ? 1 (2) 1 ep1c12 2,326,528 ? ? ? ? 1 (2) ep1c20 3,559,608 ? ? ? ? 2 (2) cyclone ii ep2c5 1,265,792 ? ? ? ? 1 ep2c8 1,983,536 ? ? ? ? 2 ep2c20 3,892,496 ? ? ? ? 3 ep2c35 6,848,608 ? ? ? ? 5 ep2c50 9,951,104 ? ? ? ? 6 ep2c70 14,319,216 ? ? ? ? 9 flex 10k epf10k10 118,000 ? ? 1 1 1 epf10k20 231,000 ? ? 1 1 1 epf10k30 376,000 ? ? 1 1 1 epf10k40 498,000 ? ? ? 1 1 epf10k50 621,000 ? ? ? 1 1 epf10k70 892,000 ? ? ? 1 1 epf10k100 1,200,000 ? ? ? ? 1 flex 10ka epf10k10a 120,000 ? ? 1 1 1 epf10k30a 406,000 ? ? 1 1 1 epf10k50v 621,000 ? ? ? 1 1 epf10k100a 1,200,000 ? ? ? ? 1 epf10k130v 1,600,000 ? ? ? ? 1 epf10k250a 3,300,000 ? ? ? ? 2 table 2. supported configuration devices (part 2 of 4) device family device data size (bits) (1) epc1064 or epc1064v epc1213 epc1441 epc1 epc2
page 4 functional description configuration devices for sram-based lut devices january 2012 altera corporation flex 10ke epf10k30e 473,720 ? ? ? 1 1 epf10k50e 784,184 ? ? ? 1 1 epf10k50s 784,184 ? ? ? 1 1 epf10k100b 1,200,000 ? ? ? ? 1 epf10k100e 1,335,720 ? ? ? ? 1 epf10k130e 1,838,360 ? ? ? ? 2 epf10k200e 2,756,296 ? ? ? ? 2 epf10k200s 2,756,296 ? ? ? ? 2 flex 6000/a epf6010a 260,000 ? ? 1 1 ? epf6016(5.0 v)/ epf6016a 260,000 ? ? 1 1 ? epf6024a 398,000 ? ? 1 1 ? flex 8000a epf8282a / epf8282av(3.3 v) 40,000 1 1 1 1 ? epf8452a 64,000 1 1 1 1 ? epf8636a 96,000 ? 1 1 1 ? epf8820a 128,000 ? 1 1 1 ? epf81188a 192,000 ? 1 1 1 ? epf81500a 250,000 ? ? 1 1 ? mercury ep1m120 1,303,120 ? ? ? ? 1 ep1m350 4,394,032 ? ? ? ? 3 stratix ep1s10 3,534,640 ? ? ? ? 3 (3) ep1s20 5,904,832 ? ? ? ? 4 ep1s25 7,894,144 ? ? ? ? 5 ep1s30 10,379,368 ? ? ? ? 7 ep1s40 12,389,632 ? ? ? ? 8 ep1s60 17,543,968 ? ???11 ep1s80 23,834,032 ? ???15 stratix gx ep1sgx10 3,534,640 ? ? ? ? 3 ep1sgx25 7,894,144 ? ? ? ? 5 ep1sgx40 12,389,632 ? ? ? ? 8 table 2. supported configuration devices (part 3 of 4) device family device data size (bits) (1) epc1064 or epc1064v epc1213 epc1441 epc1 epc2
functional description page 5 configuration devices for sram-based lut devices january 2012 altera corporation figure 1 shows the configuration device block diagram. stratix ii ep2s15 5,000,000 ? ? ? ? 3 ep2s30 10,100,000 ? ? ? ? 7 ep2s60 17,100,000 ? ???11 ep2s90 27,500,000 ? ???17 ep2s130 39,600,000 ? ???24 ep2s180 52,400,000 ? ???31 notes to ta bl e 2 : (1) raw binary file ( .rbf ) were used to determine these sizes. (2) this number is calculated with the cyclone series compression feature enabled. (3) ep1s10 es devices requires four epc2 devices. table 2. supported configuration devices (part 4 of 4) device family device data size (bits) (1) epc1064 or epc1064v epc1213 epc1441 epc1 epc2 figure 1. configuration device block diagram notes to figure 1 : (1) the epc1441 devices do not suppor t data cascadi ng. the epc1, epc2, and epc 1213 devices support data cascading. (2) the oe pin is a bidirectional open-drain pin. dclk ncs oe decode logic address data data shift register eprom array ncs decode logic address oscillator oscillator control eprom array shift register data data dclk ncasc ncasc (1) (1) fpga ( e xc e p t flex 8 000 ) co nfi gurat i o n u s in g a n ep c2 , ep c 1, or ep c 1441 flex 8 000 d e vic e co nfi gurat i o n u s in g a n ep c 1, ep c 1441, ep c 1 2 1 3 , ep c 1 0 64, or ep c 1 0 64v address counter clk ena nreset error detection circuitry oe address counter clk ena nreset (2)
page 6 device configuration configuration devices for sram-based lut devices january 2012 altera corporation device configuration the epc1, epc2, and epc1441 devices store configuration data in its erasable programmable read-only memory (eprom) array and serially clock data out using an internal oscillator. the oe , n cs , and dclk pins supply the control signals for the address counter and the data output tri-state buffer. the configuration device sends a serial bitstream of configuration data to its data pin, which is routed to the data0 input of the fpga. the control signals for configuration devices, oe , n cs , and dclk , interface directly with the fpga control signals, n status , conf _ done , and dclk . all altera fpgas can be configured by a configuration device without requiring an external intelligent controller. 1 an epc2 device cannot configure flex 8000 or flex 6000 devices. for configuration devices that support flex 8000 or flex 6000 devices, refer to tab le 2 . figure 2 shows the basic configuration interface connections between the configuration device and the altera fpga. the epc2 device allows you to begin configuration of the fpga using an additional pin, n init _ conf . the n init _ conf pin of the epc2 device can be connected to the n config pin of the fpga, which allows the init _ conf jtag instruction to begin fpga configuration. the init _ conf jtag instruction causes the epc2 device to drive the n init _ conf pin low, which in turn pulls the n config pin low. pulling the n config pin low on the fpga will reset the device. when the jtag state machine exits this state, the n init _ conf pin is released and pulled high by an internal 1-k ? resistor, which in turn pulls the n config pin high to begin configuration. if you do not use the n init _ conf pin, disconnect the n init _ conf pin, and pull the n config pin of the fpga to v cc either directly or through a resistor. figure 2. altera fpga configured using an epc1, epc2, or epc1441 configuration device (1) notes to figure 2 : (1) for more information about configuration interface connections , refer to the configuration chapter in the appropriate device handbook. (2) the n init _ conf pin which is available on epc2 devices has an internal pull-up resistor that is always active. this means an external pull-up resistor is not required on the n init _ conf / n config line. the n init _ conf pin does not need to be connected if its functionality is not used. if the n init _ conf pin is not used or unavailable, n config must be pulled to v cc either directly or through a resistor. (3) epc2 devices have internal programmable pull-up resistors on oe and n cs pins. if internal pull-up resistors are used, do not use external pull-up resistors on these pins. the internal pull-up resistors are set by default in the quartus ii software. to turn off the internal pull-up resistors, check the disable n cs a n d oe p ull-u p s o n c o n figuratio n devi c e option when you generate programming files. fpga configuration device dclk data oe (3) ncs (3) ninit_conf (2) msel dclk data0 nstatus conf_done nconfig v cc v cc gnd nce v cc nceo ncasc n.c. n.c. n (2) (3) (3)
device configuration page 7 configuration devices for sram-based lut devices january 2012 altera corporation the epc2 device?s oe and n cs pins have internal programmable pull-up resistors. if you use internal pull-up resistors, do not use external pull-up resistors on these pins. the internal pull-up resistors are set by default in the quartus ii software. to turn off the internal pull-up resistors, check the disable ncs and oe pull-ups on configuration device option when you generate programming files. the configuration device?s oe and n cs pins control the tri-state buffer on its data output pin and enable the address counter and oscillator. when the oe pin is driven low, the configuration device resets the address counter and tri-states its data pin. the n cs pin controls the data output of the configuration device. if the n cs pin is held high after the oe reset pulse, the counter is disabled and the data output pin is tri-stated. if the n cs pin is driven low after the oe reset pulse, the counter and data output pin are enabled. when oe is driven low again, the address counter is reset and the data output pin is tri-stated, regardless of the state of the n cs pin. if the fpga?s configuration data exceeds the capacity of a single epc1 or epc2 configuration device, you can cascade multiple epc1 or epc2 devices together. if multiple epc1 or epc2 devices are required, the n casc and n cs pins provide handshaking between the configuration devices. 1 epc1441 and epc1064/epc1064v devices cannot be cascaded. when configuring acex 1k, apex 20k, apex ii, arria gx, cyclone, cyclone ii, flex 10k, mercury, stratix, stratix gx, stratix ii, and stratix ii gx devices with cascaded epc1 or epc2 devices, the position of the epc1 or epc2 device in the chain determines its mode of operation. the first configuration device in the chain is the master, while subsequent configuration devices are slaves. the n init _ conf pin of the epc2 master device can be connected to the n config pin of the fpgas, which allows the init _ conf jtag instruction to begin fpga configuration. the n cs pin of the master configuration device is connected to the conf _ done pin of the fpgas, while its n casc pin is connected to the n cs pin of the next slave configuration device in the chain. additional epc1 or epc2 devices can be chained together by connecting the n casc pin to the n cs pin of the next epc1 or epc2 slave device in the chain. the last device?s n cs input comes from the previous device, while its n casc pin is left floating. all other configuration pins, dclk , data , and oe , are connected to every device in the chain. f for more information about configuration interface connections, including pull-up resistor values, supply voltages, and msel pin setting, refer to the configuration chapter in the appropriate device handbook.
page 8 device configuration configuration devices for sram-based lut devices january 2012 altera corporation figure 3 shows the basic configuration interface connections between a configuration device chain and the altera fpga. when the first device in a configuration device chain is powered-up or reset, its n cs pin is driven low because it is connected to the conf _ done pin of the fpga. because both oe and n cs pins are low, the first device in the chain recognizes it as the master device and controls configuration. since the slave devices? n cs pin is fed by the previous devices? n casc pin, its n cs pin is high after power-up and reset. in the slave configuration devices, the data output is tri-stated and dclk is an input. during configuration, the master device supplies the clock through dclk to the fpga and to any slave configuration devices. the epc1 or epc2 master device also provides the first stream of data to the fpga during multi-device configuration. after the epc1 or epc2 master device finishes sending configuration data, it tri-states its data pin to avoid contention with other configuration devices. the epc1 or epc2 master device also drives its n casc pin low, which pulls the n cs pin of the next device low. this action signals the epc1 or epc2 slave device to start sending configuration data to the fpgas. the epc1 or epc2 master device clocks all slave configuration devices until configuration is complete. when all configuration data is transferred and the n cs pin on the epc1 or epc2 master device is driven high by the fpga?s conf _ done pin, the epc1 or epc2 master device then goes into zero-power (idle) state. the epc2 master device drives data high and dclk low, while the epc1 and epc1441 device tri-state data and drive dclk low. if the n cs pin on the epc1 or epc2 master device is driven high before all configuration data is transferred, the epc1 or epc2 master device drives its oe signal low, which in turn drives the fpga?s n status pin low, indicating a configuration error. additionally, if the configuration device generates its data and detects that the conf _ done pin has not gone high, it recognizes that the fpga has not configured successfully. epc1 and epc2 devices wait for 16 dclk cycles after the last figure 3. altera fpga configured using two epc1 or epc2 configuration devices (1) notes to figure 3 : (1) for more information about configuration interface connections , refer to the configuration chapter in the appropriate device handbook. (2) the n init _ conf pin which is available on epc2 devices has an internal pull-up resistor that is always active. this means an external pull-up resistor is not required on the n init _ conf / n config line. the n init _ conf pin does not need to be connected if its functionality is not used. if the n init _ conf pin is not used or unavailable, n config must be pulled to v cc either directly or through a resistor. (3) epc2 devices have internal programmable pull-up resistors on oe and n cs pins. if internal pull-up resistors are used, do not use external pull-up resistors on these pins. the internal pull-up resistors are set by default in the quartus ii software. to turn off the internal pull-up resistors, check the disable n cs a n d oe p ull-u p s o n c o n figuratio n devi c e option when you generate programming files. v cc v cc gnd dclk data ncs oe fpga msel dclk data0 nstatus conf_done nconfig nce master configuration device slave configuration device dclk data oe (3) ncs (3) ninit_conf (2) ncasc ncasc n.c. nceo n.c. v cc (2) (3) (3) n
power and operation page 9 configuration devices for sram-based lut devices january 2012 altera corporation configuration bit was sent for the conf _ done pin to reach a high state. in this case, the configuration device pulls its oe pin low, which in turn drives the target device?s n status pin low. configuration automatically restarts if the auto-restart configuration on error option is turned on in the quartus ii software from the general tab of the device & pin options dialog box or the max+plus ii software?s global project device options dialog box (assign menu). f for more information about fpga configuration and configuration interface connections between configuration devices and altera fpgas, refer to the configuration chapter in the appropriate device handbook. power and operation this section describes power-on reset (por) delay, error detection, and 3.3-v and 5.0-v operation of altera configuration devices. power-on reset during initial power-up, a por delay occurs to permit voltage levels to stabilize. when configuring an fpga with one epc1, epc2, or epc1441 device, the por delay occurs inside the configuration device and the por delay is a maximum of 200 ms. when configuring a flex 8000 device with one epc1213, epc1064, or epc1064v device, the por delay occurs inside the flex 8000 device and the por delay is typically 100 ms, with a maximum of 200 ms. during por, the configuration device drives its oe pin low. this low signal delays configuration because the oe pin is connected to the target fpga?s n status pin. when the configuration device completes por, it releases its open-drain oe pin, which is then pulled high by a pull-up resistor. 1 you should power up the fpga before the configuration device exits por to avoid the master configuration device from entering slave mode. if the fpga is not powered up before the configuration device exits por, the conf _ done / n cs line is high because of the pull-up resistor. when the configuration device exits por and releases oe , it sees n cs high, which signals the configuration device to enter slave mode. therefore, configuration will not begin because the data output is tri-stated and dclk is an input pin in slave mode. error detection circuitry the epc1, epc2, and epc1441 configuration devices have built-in error detection circuitry for configuring acex 1k, apex 20k, apex ii, arria gx, cyclone, cyclone ii, flex 10k, flex 6000, mercury, stratix, stratix gx, stratix ii, or stratix ii gx devices. built-in error detection circuitry uses the n cs pin of the configuration device, which monitors the conf _ done pin on the fpga. if the n cs pin on the epc1 or epc2 master device is driven high before all configuration data is transferred, the epc1 or epc2 master device drives its oe signal low, which in turn drives the fpga?s n status pin low, indicating a configuration error. additionally, if the configuration device generates its data and detects that the conf _ done pin has not gone high, it recognizes
page 10 power and operation configuration devices for sram-based lut devices january 2012 altera corporation that the fpga has not configured successfully. epc1 and epc2 devices wait for 16 dclk cycles after the last configuration bit was sent for the conf _ done pin to reach a high state. in this case, the configuration device pulls its oe pin low, which in turn drives the target device?s n status pin low. configuration automatically restarts if the auto-restart configuration on error option is turned on in the quartus ii software from the general tab of the device & pin options dialog box or the max+plus ii software?s global project device options dialog box (assign menu). in addition, if the fpga detects a cyclic redundancy check (crc) error in the received data, it will flag the error by driving the n status signal low. this low signal on n status drives the oe pin of the configuration device low, which resets the configuration device. crc checking is performed when configuring all altera fpgas. 3.3-v or 5.0-v operation power the epc1, epc2, and epc 1441 configuration device at 3.3 v or 5.0 v. for each configuration device, an option must be set for the 3.3-v or 5.0-v operation. for epc1 and epc1441 configuration devices, 3.3-v or 5.0-v operation is controlled by a programming bit in the .pof . the low-voltage mode option in the options tab of the configuration device options dialog box in the quartus ii software or the use low-voltage configuration eprom option in the global project device options dialog box (assign menu) in the max+plus ii software sets this parameter. for example, epc1 devices are programmed automatically to operate in 3.3-v mode when configuring flex 10ka devices, which have a v cc voltage of 3.3 v. in this example, the epc1 device?s vcc pin is connected to a 3.3-v power supply. for epc2 devices, this option is set externally by the vccsel pin. in addition, the epc2 device has an externally controlled option, set by the vppsel pin, to adjust the programming voltage to 5.0 v or 3.3 v. the functions of the vccsel and vppsel pins are described below. these pins are only available in the epc2 devices. vccsel pin?for epc2 configuration devices, 5.0-v or 3.3-v operation is controlled by the vccsel option pin. the device functions in 5.0-v mode when vccsel is connected to gnd and 3.3-v mode when vccsel is connected to v cc . vppsel pin?the v pp programming power pin of the epc2 device is normally tied to v cc . for epc2 devices operating at 3.3 v, it is possible to improve isp time by setting v pp to 5.0 v. for all other configuration devices, v pp must be tied to v cc . the vppsel pin of the epc2 device must be set in accordance with the vpp pin of the epc2 device. if the vpp pin is supplied by a 5.0-v power supply, vppsel must be connected to gnd and if the vpp pin is supplied by a 3.3-v power supply, vppsel must be connected to v cc .
power and operation page 11 configuration devices for sram-based lut devices january 2012 altera corporation ta b l e 3 lists the relationship between the v cc and v pp voltage levels and the required logic level for vccsel and vppsel pins. a high logic level means the pin should be connected to v cc , while a low logic level means the pin should be connected to gnd. at a 3.3-v operation, all epc2 inputs are 5.0-v tolerant, except for data , dclk , and n casc pins. the data and dclk pins are used only to interface between the epc2 device and the fpga it is configuring. ta b l e 4 lists the voltage tolerences of all epc2 device pins. if one epc1, epc2, or epc1441 configuration device is powered at 3.3 v, the n status and conf _ done pull-up resistors must be connected to 3.3 v. if these configuration devices are powered at 5.0 v, the n status and conf _ done pull-up resistors can be connected to either 3.3 v or 5.0 v. table 3. vccsel and vppsel pin functions on the epc2 device vcc voltage level (v) vpp voltage level (v) vccsel pin logic level vppsel pin logic level 3.3 3.3 high high 3.3 5.0 high low 5.0 5.0 low low table 4. epc2 device input and bidirectional pin voltage tolerance pin 5.0-v operation 3.3-v operation 5.0-v tolerant 3.3-v tolerant 5.0-v tolerant 3.3-v tolerant data vv ? v dclk vv ? v n casc vv ? v oe vvvv n cs vvvv vccsel vvvv vppsel vvvv n init_conf vvvv tdi vvvv tms vvvv tck vvvv
page 12 programming and configuration file support configuration devices for sram-based lut devices january 2012 altera corporation programming and configuration file support the quartus ii and max+plus ii softwares provide programming support for altera configuration devices. during compilation, the quartus ii and max+plus ii softwares automatically generates a .pof , which is used to program the configuration devices. in a multi-device configuration, the software combines the programming files for multiple acex 1k, apex 20k, apex ii, arria gx, cyclone, cyclone ii, flex 10k, mercury, stratix, stratix gx, stratix ii, and stratix ii gx devices into one or more configuration devices. the software allows you to select the appropriate configuration device to store the data for each fpga. all altera configuration devices are programmable using altera programming hardware in conjunction with the quartus ii or max+plus ii software. in addition, many third-party programmers offer programming hardware that supports altera configuration devices. 1 an epc2 device can be programmed with a .pof generated for an epc1 or epc1441 device. an epc1 device can be programmed with a .pof generated for an epc1441 device. epc2 configuration devices can be programmed in-system through its industry-standard four-pin jtag interface. isp capability in the epc2 devices provide ease in prototyping and fpga functionality. when programming multiple epc2 devices in a jtag chain, the quartus ii and max+plus ii softwares and other programming methods employ concurrent programming to simultaneously program multiple devices and reduce programming time. epc2 devices can be programmed and erased up to 100 times. after programming an epc2 device in-system, fpga configuration is initiated by the init _ conf jtag instruction of the epc2 device. for more information, refer to ta b l e 6 . f for more information about programming and configuration support, refer to the following documents: altera programming hardware data sheet usb-blaster download cable user guide masterblaster serial/usb communications cable user guide byteblaster ii download cable user guide byteblastermv download cable user guide bitblaster serial download cable data sheet you can also program the configuration devices using the quartus ii or max+plus ii software with the apu or the appropriate configuration device programming adapter.
programming and configuration file support page 13 configuration devices for sram-based lut devices january 2012 altera corporation ta b l e 5 lists the programming adapter to use with each configuration device. to program altera configuration devices using the quartus ii software and the apu, follow these steps: 1. choose the quartus ii programmer (tools menu). 2. load the appropriate .pof by clicking add . the device column displays the device for the current programming file. 3. insert a blank configuration device into the programming adapter?s socket. 4. turn on the program/configure . you can also turn on verify to verify the contents of a programmed device against the programming data loaded from a programming file. 5. click start . 6. after successful programming, you can place the configuration device on the pcb to configure the fpga device. to program altera configuration devices using the max+plus ii software and the apu, follow these steps: 1. open the max+plus ii programmer. 2. load the appropriate .pof using the select programming file dialog box (file menu). by default, the programmer loads the current project?s .pof . the device field displays the device for the current programming file. 3. insert a blank configuration device into the programming adapter?s socket. 4. click program . 5. after successful programming, you can place the configuration device on the pcb to configure the fpga device. if you are cascading epc1 or epc2 devices, you must generate multiple .pof . the first device .pof have the same name as the project, while the second device .pof have the same name as the first, but with a ?_1? extension (e.g., top_1.pof ). table 5. programming adapters device package adapter epc2 20 - pin j-lead plmj1213 32-pin tqfp plmt1213 epc1 8-pin dip plmj1213 20-pin j-lead plmj1213 epc1441 8-pin dip plmj1213 20-pin j-lead plmj1213 32-pin tqfp plmt1064
page 14 ieee std. 1149.1 (jtag) boundary-scan testing configuration devices for sram-based lut devices january 2012 altera corporation ieee std. 1149.1 (jtag) boundary-scan testing the epc2 device provides jtag bst circuitry that complies with the ieee std. 1149.1-1990 specification. you can perform jtag bst before or after configuration, but not during configuration. table 6 lists the jtag instructions supported by the epc2 device. f for more information, refer to an39: ieee 1149.1 jtag boundary-scan testing in altera devices . table 6. epc2 device jtag instructions jtag instruction opcode description sample/preload 00 0101 0101 allows a snapshot of a signal at the device pins to be captured and examined during normal device operation and permits an initial data pattern output at the device pins. extest 00 0000 0000 allows the external circuitry and board-level interconnections to be tested by forcing a test pattern at the output pins and capturing results at the input pins. bypass 11 1111 1111 places the 1-bit bypass register between the tdi and tdo pins, which allows the bst data to pass synchronously through a selected device to adjacent devices during normal device operation. idcode 00 0101 1001 selects the device idcode register and places it between the tdi and tdo pins, allowing the device idcode to be serially shifted out of the tdo pin. the device idcode for the epc2 configuration device is shown below: 0000 0001000000000010 00001101110 1 usercode 00 0111 1001 selects the usercode register and places it between the tdi and tdo pins, allowing the usercode to be serially shifted out of the tdo pin. the 32-bit usercode is a programmable user-defined pattern. init_conf 00 0110 0001 initiates the fpga re-configuration process by pulsing the n init_conf pin low, which is connected to the fpgas n config pins. after this instruction is updated, the n init_conf pin is pulsed low when the jtag state machine enters the run-test/idle state. the n init_conf pin is then released and nconfig is pulled high by the resistor after the jtag state machine goes out of run-test/idle state. the fpga configuration starts after the n config pin goes high. as a result, the fpga is configured with the new configuration data stored in the configuration device. you can add this function to your programming file ( . p of , .jam , .jb c ) in the quartus ii software by enabling the i n itiate c o n figuratio n after p rogrammi n g option in the programmer options window (options menu). this instruction is also used by the max+plus ii software, .jam files, and .jb c files. isp instructions ? these instructions are used when programming an epc2 device using jtag ports with a usb-blaster, masterblaster, byteblaster ii, ethernetblaster, or byteblastermv download cable, or using a .jam , .jb c , or .svf file using an embedded processor.
ieee std. 1149.1 (jtag) boundary-scan testing page 15 configuration devices for sram-based lut devices january 2012 altera corporation figure 4 shows the timing requirements for the jtag signals. ta b l e 7 lists the timing parameters and values for configuration devices. figure 4. epc2 device jtag waveforms table 7. jtag timing parameters and values symbol parameter min max unit t jcp tck clock period 100 ? ns t jch tck clock high time 50 ? ns t jcl tck clock low time 50 ? ns t jpsu jtag port setup time 20 ? ns t jph jtag port hold time 45 ? ns t jpco jtag port clock to output ? 25 ns t jpzx jtag port high impedance to valid output ? 25 ns t jpxz jtag port valid output to high impedance ? 25 ns t jssu capture register setup time 20 ? ns t jsh capture register hold time 45 ? ns t jsco update register clock to output ? 25 ns t jszx update register high impedance to valid output ? 25 ns t jsxz update register valid output to high impedance ? 25 ns tdo tck t jpzx t jpco t jph t jpxz t jcp t jpsu t jcl t jch tdi tms si g nal to be captured si g nal to be driven t jszx t jssu t jsh t jsco t jsxz
page 16 timing information configuration devices for sram-based lut devices january 2012 altera corporation timing information figure 5 shows the timing waveform when using a configuration device. ta b l e 8 lists the timing parameters when using epc2 devices at 3.3 v. figure 5. timing waveform using a configuration device note to figure 5 : (1) the epc2 device drives dclk low and data high after configuration. the epc1 and epc1441 devices drive dclk low and tri-state data after configuration. dd d d 0 1 2 3 d n tr i - s t a t e user mode (1) t oezx t por t ch t cl t dsu t co t dh tr i - s t a t e oe/nstatus ncs/conf_done dclk data user i/o init_done ninit_conf or vcc/nconfig table 8. timing parameters when using epc2 devices at 3.3 v symbol parameter min typ max units t por por delay (1) ??200ms t oezx oe high to data output enabled ? ? 80 ns t ce oe high to first rising edge on dclk ??300ns t dsu data setup time before rising edge on dclk 30 ? ? ns t dh data hold time after rising edge on dclk 0??ns t co dclk to data out ? ? 30 ns t cdoe dclk to data enable/disable ? ? 30 ns f clk dclk frequency 5 7.7 12.5 mhz t mch dclk high time for the first device in the configuration chain 40 65 100 ns t mcl dclk low time for the first device in the configuration chain 40 65 100 ns t sch dclk high time for subsequent devices 40 ? ? ns t scl dclk low time for subsequent devices 40 ? ? ns t casc dclk rising edge to n casc ? ? 25 ns t cca n cs to ncasc cascade delay ? ? 15 ns t oew oe low pulse width (reset) to guarantee counter reset 100 ? ? ns t oec oe low (reset) to dclk disable delay ? ? 30 ns t nrcas oe low (reset) to n casc delay ? ? 30 ns note to tab l e 8 : (1) during initial power-up, a por delay occurs to permit voltage levels to stabilize. subsequent reconfigurations do not incur this delay.
timing information page 17 configuration devices for sram-based lut devices january 2012 altera corporation ta b l e 9 lists the timing parameters when using epc1 and epc1441 devices at 3.3 v. ta b l e 1 0 lists the timing parameters when using epc1, epc2, and epc1441 devices at 5.0 v. table 9. timing parameters when using epc1 and epc1441 devices at 3.3 v symbol parameter min typ max units t por por delay (1) ??200ms t oezx oe high to data output enabled ? ? 80 ns t ce oe high to first rising edge on dclk ??300ns t dsu data setup time before rising edge on dclk 30 ? ? ns t dh data hold time after rising edge on dclk 0??ns t co dclk to data out ? ? 30 ns t cdoe dclk to data enable/disable ? ? 30 ns f clk dclk frequency 2 4 10 mhz t mch dclk high time for the first device in the configuration chain 50 125 250 ns t mcl dclk low time for the first device in the configuration chain 50 125 250 ns t sch dclk high time for subsequent devices 50 ? ? ns t scl dclk low time for subsequent devices 50 ? ? ns t casc dclk rising edge to n casc ? ? 25 ns t cca n cs to n casc cascade delay ? ? 15 ns t oew oe low pulse width (reset) to guarantee counter reset 100 ? ? ns t oec oe low (reset) to dclk disable delay ? ? 30 ns t nrcas oe low (reset) to n casc delay ? ? 30 ns note to tab l e 9 : (1) during initial power-up, a por delay occurs to permit voltage levels to stabilize. subsequent reconfigurations do not incur this delay. table 10. timing parameters when using epc1, epc2, and epc1441 devices at 5.0 v (part 1 of 2) symbol parameter min typ max units t por por delay (1) ??200ms t oezx oe high to data output enabled ? ? 50 ns t ce oe high to first rising edge on dclk ??200ns t dsu data setup time before rising edge on dclk 30 ? ? ns t dh data hold time after rising edge on dclk 0??ns t co dclk to data out ? ? 20 ns t cdoe dclk to data enable/disable ? ? 20 ns f clk dclk frequency 6.7 10 16.7 mhz t mch dclk high time for the first device in the configuration chain 30 50 75 ns t mcl dclk low time for the first device in the configuration chain 30 50 75 ns t sch dclk high time for subsequent devices 30 ? ? ns t scl dclk low time for subsequent devices 30 ? ? ns t casc dclk rising edge to n casc ? ? 20 ns t cca ncs to n casc cascade delay ? ? 10 ns
page 18 timing information configuration devices for sram-based lut devices january 2012 altera corporation ta b l e 11 lists the timing parameters when using epc1, epc1064, epc1064v, epc1213, and epc1441 devices when configuring the flex 8000 device. t oew oe low pulse width (reset) to guarantee counter reset 100 ? ? ns t oec oe low (reset) to dclk disable delay ? ? 20 ns t nrcas oe low (reset) to n casc delay ? ? 25 ns note to tab l e 1 0 : (1) during initial power-up, a por delay occurs to permit voltage levels to stabilize. subsequent reconfigurations do not incur this delay. table 10. timing parameters when using epc1, epc2, and epc1441 devices at 5.0 v (part 2 of 2) symbol parameter min typ max units table 11. flex 8000 device configuration parameters using epc1, epc1064, epc1064v, epc1213, and epc1441 devices symbol parameter epc1064v epc1064 and epc1213 epc1 and epc1441 unit min max min max min max t oezx oe high to data output enabled ? 75 ? 50 ? 50 ns t cszx n cs low to data output enabled ? 75 ? 50 ? 50 ns t csxz n cs high to data output disabled ? 75 ? 50 ? 50 ns t css n cs low setup time to first dclk rising edge 150 ? 100 ? 50 ? ns t csh n cs low hold time after dclk rising edge 0?0?0?ns t dsu data setup time before rising edge on dclk 75 ? 50 ? 50 ? ns t dh data hold time after rising edge on dclk 0?0?0?ns t co dclk to data out delay ? 100 ? 75 ? 75 ns t ck clock period 240 ? 160 ? 100 ? ns f ck clock frequency ? 4 ? 6 ? 8 mhz t cl dclk low time 120 ? 80 ? 50 ? ns t ch dclk high time 120 ? 80 ? 50 ? ns t xz oe low or n cs high to data output disabled ? 75 ? 50 ? 50 ns t oew oe pulse width to guarantee counter reset 150 ? 100 ? 100 ? ns t casc last dclk + 1 to n casc low delay ? 90 ? 60 ? 50 ns t ckxz last dclk + 1 to data tri-state delay ? 75 ? 50 ? 50 ns t ceout n cs high to n casc high delay ? 150 ? 100 ? 100 ns
operating conditions page 19 configuration devices for sram-based lut devices january 2012 altera corporation operating conditions ta b l e 1 2 through ta b l e 1 9 list information about absolute maximum ratings, recommended operating conditions, dc operating conditions, and capacitance for configuration devices. table 12. absolute maximum ratings (1) symbol parameter conditions min max unit v cc supply voltage with respect to gnd (2) ?2.0 7.0 v v i dc input voltage with respect to gnd (2) ?2.0 7.0 v i max dc v cc or gnd current ? ? 50 ma i out dc output current, per pin ? ?25 25 ma p d power dissipation ? ? 250 mw t stg storage temperature no bias ?65 150 c t amb ambient temperature under bias ?65 135 c t j junction temperature under bias ? 135 c table 13. recommended operating conditions symbol parameter conditions min max unit v cc supply voltage for 5.0-v operation (3) , (4) 4.75 (4.50) 5.25 (5.50) v supply voltage for 3.3-v operation (3) , (4) 3.0 (3.0) 3.6 (3.6) v v i input voltage with respect to gnd ?0.3 v cc + 0.3 (5) v v o output voltage ? 0 v cc v t a operating temperature for commercial use 0 70 c for industrial use ?40 85 c t r input rise time ? ? 20 ns t f input fall time ? ? 20 ns table 14. dc operating conditions symbol parameter conditions min max unit v ih high-level input voltage ? 2.0 v cc + 0.3 (5) v v il low-level input voltage ? ?0.3 0.8 v v oh 5.0-v mode high-level ttl output voltage i oh = ?4 ma dc (6) 2.4 ? v 3.3-v mode high-level cmos output voltage i oh = ?0.1 ma dc (6) v cc ? 0.2 ? v v ol low-level output voltage i ol = 4 ma dc (6) ?0.4 v i i input leakage current v i = v cc or gnd ?10 10 ? a i oz tri-state output off-state current v o = v cc or gnd ?10 10 ? a
page 20 operating conditions configuration devices for sram-based lut devices january 2012 altera corporation table 15. epc1064, epc1064v, and epc1213 devices i cc supply current values symbol parameter conditions min typ max u n it i cc0 v cc supply current (standby) ? ? 100 200 ? a i cc1 v cc supply current (during configuration) ? ? 10 50 ma table 16. epc2 device values symbol parameter conditions min typ max unit i cc0 v cc supply current (standby) v cc = 5.0 v or 3.3 v ? 50 100 a i cc1 v cc supply current (during configuration) v cc = 5.0 v or 3.3 v ? 18 50 ma r conf configuration pins internal pull up ( oe , n cs , n init _ conf ) ?1?k ? table 17. epc1 device i cc supply current values symbol parameter conditions min typ max unit i cc0 v cc supply current (standby) ? ? 50 100 a i cc1 v cc supply current (during configuration) v cc = 5.0 v ? 30 50 ma v cc = 3.3 v ? 10 16.5 ma table 18. epc1441 device i cc supply current values symbol parameter conditions min typ max unit i cc0 v cc supply current (standby) ? ? 30 60 a i cc1 v cc supply current (during configuration) v cc = 5.0 v ? 15 30 ma i cc1 v cc supply current (during configuration) v cc = 3.3 v ? 5 10 ma table 19. capacitance (7) symbol parameter conditions min max unit c in input pin capacitance v in = 0 v, f = 1.0 mhz ? 10 pf c out output pin capacitance v out = 0 v, f = 1.0 mhz ? 10 pf notes to ta bl e 12 through ta bl e 19 : (1) for more information, refer to the operating requirements for altera devices datasheet . (2) the minimum dc input is -0.3 v. during transitions, the inputs may undershoot to -2.0 v or overshoot to 7.0 v for input current s less than 100 ma and periods shorter than 20 ns under no-load conditions. (3) numbers in parentheses are for industrial temperature range devices. (4) maximum v cc rise time is 100 ms. (5) certain epc2 device pins are driven to 5.75 v when operated with a 3.3-v v cc . for more information, refer to table 4 on page 11 . (6) the i oh parameter refers to high-level ttl or cmos output current and the i ol parameter refers to low-level ttl or cmos output current. (7) capacitance is sample tested only.
pin information page 21 configuration devices for sram-based lut devices january 2012 altera corporation pin information ta b l e 2 0 lists the pin functions of the epc1, epc2, and epc1441 devices during device configuration. f for more information about pin information of epc devices, refer to the enhanced configuration (epc) devices datasheet . f for more information about pin information of epcs devices, refer to the serial configuration (epcs) devices datasheet . table 20. epc1, epc2, and epc1441 device pin functions during configuration (part 1 of 3) pin name pin number pin type description 8-pin pdip (1) 20-pin plcc 32-pin tqfp (2) data 1231output serial data output. the data pin connects to the data0 pin of the fpga. data is latched into the fpga on the rising edge of dclk . the data pin is tri-stated before configuration and when the n cs pin is high. after configuration, the epc2 device drives data high, while the epc1 and epc1441 device tri-state data . dclk 2 4 2 bidirectional clock output when configuring with a single configuration device or when the configuration device is the first (master) device in a chain. clock input for the next (slave) configuration devices in a chain. the dclk pin connects to the dclk pin of the fpga. rising edges on dclk increment the internal address counter and present the next bit of data on the data pin. the counter is incremented only if the oe input is held high, the n cs input is held low, and all configuration data has not been transferred to the target device. after configuration or when oe is low, the epc1, epc2 and epc1441 device drive dclk low. oe 387 open-drain bidirectional output enable (active high) and reset (active low). the oe pin connects to the n status pin of the fpga. a low logic level resets the address counter. a high logic level enables data and the address counter to count. if this pin is low (reset) during configuration, the internal oscillator becomes inactive and dclk drives low. for more information, refer to ?error detection circuitry? on page 9 . the oe pin has an internal programmable 1-k ? resistor in epc2 devices. if internal pull-up resistors are used, do not use external pull-up resistors on these pins. you can disable the internal pull-up resistors through the disable ncs a n d oe p ull-u p s o n c o n figuratio n devi c e option.
page 22 pin information configuration devices for sram-based lut devices january 2012 altera corporation n cs 4910input chip select input (active low). the n cs pin connects to the conf _ done pin of the fpga. a low input allows dclk to increment the address counter and enables data to drive out. if the epc1 or epc2 device is reset ( oe pulled low) while n cs is low, the device initializes as the master device in a configuration chain. if the epc1 or epc2 device is reset ( oe pulled low) while n cs is high, the device initializes as a slave device in the chain. the n cs pin has an internal programmable 1-k ? resistor in epc2 devices. if internal pull-up resistors are used, do not use external pull-up resistors on these pins. you can disable the internal pull-up resistors through the disable n cs a n d oe p ull-u p s o n c o n figuratio n devi c e option. n casc 61215output cascade select output (active low). this output goes low when the address counter has reached its maximum value. when the address counter has reached its maximum value, the configuration device has sent all its configuration data to the fpga. in a chain of epc1 or epc2 devices, the n casc pin of one device is connected to the n cs pin of the next device, which permits dclk to clock data from the next epc1 or epc2 device in the chain. for single epc1 or epc2 device and the last device in the chain, n casc is left floating. this pin is only available in epc1 and epc2 devices, which support data cascading. n init _ conf n/a 13 16 open-drain output allows the init _ conf jtag instruction to initiate configuration. the n init _ conf pin connects to the n config pin of the fpga. if multiple epc2 devices are used to configure an fpga, the n init _ conf of the first epc2 device pin is tied to the fpga?s n config pin, while subsequent devices' n init _ conf pins are left floating. the init _ conf pin has an internal 1-k ? pull-up resistor that is always active in epc2 devices. this pin is only available in epc2 devices. tdi n/a 11 13 input jtag data input pin. connect this pin to v cc if the jtag circuitry is not used. this pin is only available in epc2 devices. tdo n/a 1 28 output jtag data output pin. do not connect this pin if the jtag circuitry is not used. this pin is only available in epc2 devices. tms n/a 19 25 input jtag mode select pin. connect this pin to v cc if the jtag circuitry is not used. this pin is only available in epc2 devices. table 20. epc1, epc2, and epc1441 device pin functions during configuration (part 2 of 3) pin name pin number pin type description 8-pin pdip (1) 20-pin plcc 32-pin tqfp (2)
pin information page 23 configuration devices for sram-based lut devices january 2012 altera corporation tck n/a 3 32 input jtag clock pin. connect this pin to gnd if the jtag circuitry is not used. this pin is only available in epc2 devices. vccsel n/a 5 3 input mode select for v cc supply. vccsel must be connected to gnd if the device uses a 5.0-v power supply (v cc = 5.0 v). vccsel must be connected to v cc if the device uses a 3.3-v power supply (v cc = 3.3 v). this pin is only available in epc2 devices. vppsel n/a 14 17 input mode select for v pp . supply. vppsel must be connected to gnd if v pp uses a 5.0-v power supply (v pp = 5.0 v). vppsel must be connected to v cc if v pp uses a 3.3-v power supply (v pp = 3.3 v). this pin is only available in epc2 devices. vpp n/a 18 23 power programming power pin. for the epc2 device, this pin is normally tied to v cc . if the v cc of the epc2 device is 3.3 v, tie v pp to 5.0 v to improve isp time. for epc1 and epc1441 devices, v pp must be tied to v cc . this pin is only available in epc2 devices. vcc 7, 8 20 27 power power pin. gnd 5 10 12 ground ground pin. place a 0.2-f decoupling capacitor between the vcc and gnd pins. notes to ta bl e 20 : (1) this package is available for epc1 and epc1441 devices only. (2) this package is available for epc2 and epc1441 devices only. table 20. epc1, epc2, and epc1441 device pin functions during configuration (part 3 of 3) pin name pin number pin type description 8-pin pdip (1) 20-pin plcc 32-pin tqfp (2)
page 24 package configuration devices for sram-based lut devices january 2012 altera corporation package figure 6 and figure 7 show the configuration device package pin-outs. f for more information about package outlines and drawings, refer to the package and thermal resistance page. figure 6. epc1, epc1064, epc1064v, epc1213, and epc1441 package pin-out diagrams (1) notes to figure 6 : (1) epc1 and epc1441 devices are one-time programmable devices. isp is not available in these devices. (2) the n casc pin is available on epc1 devices, which allo ws them to be cascaded. for epc1441 devices, n casc is a reserved pin and should be left unconnected. figure 7. epc2 package pin-out diagrams 8-pin pdip 32-pin tqfp epc1441 epc1064 epc1064v 20-pin plcc epc1 epc1441 epc1213 epc1064 epc1064v epc1 epc1441 epc1213 epc1064 epc1064v data dclk oe ncs vcc vcc ncasc (2) gnd 1 2 3 4 8 7 6 5 1 2 3 4 5 6 7 8 20 19 10 13 18 17 16 15 14 oe n.c. n.c. n.c. n.c. n.c. n.c. n.c. dclk n.c. n.c. n.c. data vcc vcc n.c. n.c. (2) ncasc ncs gnd 30 31 32 1 2 3 4 5 29 28 dclk n.c. n.c. n.c. n.c. n.c. n.c. n.c. n.c. n.c. n.c. n.c. n.c. n.c. ncs gnd 24 23 22 21 20 vcc 19 18 17 n.c. n.c. n.c. n.c. n.c. n.c. n.c. n.c. n.c. n.c. n.c. n.c. data vcc 25 916 8 oe 6 7 10 11 12 13 14 15 27 26 91112 32-pin tqfp 20-pin plcc 1 2 3 4 5 6 7 8 20 19 11 10 91213 18 17 16 15 14 oe n.c. vccsel dclk n.c. tms tck data tdo vcc vpp n.c. n.c. n.c. vppsel tdi ncasc ncs gnd 30 31 32 1 2 3 4 5 29 28 n.c. n.c. dclk n.c. vccsel tdi n.c. ncs n.c. gnd ninit_conf n.c. n.c. 24 23 22 21 20 n.c. vpp n.c. n.c. 19 18 17 tdo tck data n.c. n.c. tms vcc n.c. 25 9 16 8 n.c. oe n.c. vppsel n.c. n.c. 6 7 10 11 12 13 14 15 27 26 ncasc ninit_conf
ordering codes page 25 configuration devices for sram-based lut devices january 2012 altera corporation ordering codes ta b l e 2 1 lists the ordering codes for the epc1, epc2, and epc1441 configuration devices. document revision history ta b l e 2 2 lists the revision history for this document. table 21. configuration device ordering codes device package temperature ordering code epc1 20-pin plcc commercial epc1lc20 epc1 20-pin plcc industrial epc1li20 epc1 8-pin pdip commercial epc1pc8 epc1 8-pin pdip industrial epc1pi8 epc2 32-pin tqfp commercial epc2tc32 epc2 32-pin tqfp industrial EPC2TI32 epc2 20-pin plcc commercial epc2lc20 epc2 20-pin plcc industrial epc2li20 epc1441 32-pin tqfp commercial epc1441tc32 epc1441 32-pin tqfp industrial epc1441ti32 epc1441 20-pin plcc commercial epc1441lc20 epc1441 20-pin plcc industrial epc1441li20 epc1441 8-pin pdip commercial epc1441pc8 epc1441 8-pin pdip industrial epc1441pi8 table 22. document revision history date version changes january 2012 3.0 minor text edits. december 2009 2.4 updated ?features? section. removed ?referenced documents? section. october 2008 2.3 updated ?features? and ?ieee std. 1149.1 (jtag) boundary-scan testing? sections. updated table 5?2 and table 5?16. added ?referenced documents? section. updated new document format. april 2007 2.2 added document revision history. july 2004 2.0 added stratix ii and cyclone ii device information throughout chapter. september 2003 1.0 initial release.
page 26 document revision history configuration devices for sram-based lut devices january 2012 altera corporation

▲Up To Search▲

Price & Availability of EPC2TI32

	To Download EPC2TI32 Datasheet File
If you can't view the Datasheet, Please click here to try to view without PDF Reader .